feat : update studio docs#675
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
mishramonalisha76
left a comment
There was a problem hiding this comment.
Can we add a small video of creating agent, team and workflows , individual pages or maybe one in the overview ?
Can we make all the image to be of the whole app witht he sidebar and topbar?
| | **Input/Output Schema** | Structured I/O using registered Pydantic schemas | | ||
| | **Memory** | Enable memory for multi-turn conversations | | ||
| | **Knowledge** | Attach knowledge bases for RAG | | ||
| - **Model**: select from registered models. |
There was a problem hiding this comment.
Should we also give the sdk version from when studio is available ?
| | [Teams](/agent-os/studio/teams) | Compose multi-agent teams with coordination modes | | ||
| | [Workflows](/agent-os/studio/workflows) | Design step-based workflows with conditions, loops, routers, and parallel execution | | ||
| | [Registry](/agent-os/studio/registry) | Browse and manage registered tools, models, databases, and schemas | | ||
| **[Agents](/agent-os/studio/agents)** |
There was a problem hiding this comment.
| **[Agents](/agent-os/studio/agents)** | |
| **[Agents](/agent-os/studio/agents)** : |
| **[Workflows](/agent-os/studio/workflows)** | ||
| Orchestrate agents and teams into step-based pipelines. Control the flow with loops, conditions, routers, and parallel execution. | ||
|
|
||
| use functions or cel expressions to evaluate conditions and selectors. |
There was a problem hiding this comment.
Does this belong to workflows only or agent and teams too ? looks like an orphaned line
| Add tools, models, databases, and schemas that Studio can use to build agents, teams, and workflows. | ||
|
|
||
| Register agents and teams in the `Registry` to reuse them as members in Studio teams and as steps in Studio workflows. | ||
|
|
||
| Register `knowledge`, `memory_managers`, and `session_summary_managers` for agents and teams to use. |
There was a problem hiding this comment.
| Add tools, models, databases, and schemas that Studio can use to build agents, teams, and workflows. | |
| Register agents and teams in the `Registry` to reuse them as members in Studio teams and as steps in Studio workflows. | |
| Register `knowledge`, `memory_managers`, and `session_summary_managers` for agents and teams to use. | |
| Register the components Studio composes with: tools, models, databases, schemas, knowledge, `memory_managers`, and `session_summary_managers`. Register existing agents and teams to reuse them as members in Studio teams or steps in Studio workflows. |
|
|
||
| Save your work as a draft version. Drafts are not accessible via the API but can be tested, restored, and published later. You can save multiple draft versions to checkpoint your progress. | ||
|
|
||
| ### 2. Save Draft or publish directly |
There was a problem hiding this comment.
| ### 2. Save Draft or publish directly | |
| ### 2. Save Draft or Publish Directly |
| | **Success Criteria** | Define when the team's task is complete | | ||
| Create a new team by using existing agents and teams from your Registry or built in Studio, and configuring the team settings: | ||
|
|
||
| - **Team Members and Execution**: select agents or teams to include as members, and set the team mode and delegation behavior. read more about [team members and execution](/agent-os/studio/teams#team-members-and-execution) here. |
There was a problem hiding this comment.
| - **Team Members and Execution**: select agents or teams to include as members, and set the team mode and delegation behavior. read more about [team members and execution](/agent-os/studio/teams#team-members-and-execution) here. | |
| - **Team Members and Execution**: select agents or teams to include as members, and set the team mode and delegation behavior. Read more about [team members and execution](/agent-os/studio/teams#team-members-and-execution) here. |
| ### Team Members and Execution | ||
|
|
||
| - **Members**: select the agents or teams to include as members. | ||
| - **Team Mode** _(optional)_: controls how the team leader coordinates work with member agents: |
There was a problem hiding this comment.
We should attach some reference doc for this if available
| - **Route** | ||
| - **Broadcast** | ||
| - **Tasks** | ||
| - **Respond Directly**: let the team leader respond on its own instead of delegating. |
There was a problem hiding this comment.
| - **Respond Directly**: let the team leader respond on its own instead of delegating. | |
| - **Respond Directly**: lets the team leader respond on its own instead of delegating. |
| - **Broadcast** | ||
| - **Tasks** | ||
| - **Respond Directly**: let the team leader respond on its own instead of delegating. | ||
| - **Delegate to All Members**: send the task to every member at once. |
There was a problem hiding this comment.
| - **Delegate to All Members**: send the task to every member at once. | |
| - **Delegate to All Members**: sends the task to every member at once. |
|
|
||
|
|
||
|
|
||
| example of registry configuration: |
There was a problem hiding this comment.
| example of registry configuration: | |
| Example of registry configuration: |
mishramonalisha76
left a comment
There was a problem hiding this comment.
Lets also connect each page to the respective API reference
Description
Describe key changes, mention related issues or motivation for the changes.
Note: Your PR title must follow conventional commit format (e.g.,
docs: add auth guide,fix: correct broken links,style: update formatting). See CONTRIBUTING.md for details.Type of Change
Related Issues/PRs (if applicable)
Checklist